home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20041116-20060924
/
000018_fdc@columbia.edu_Fri Dec 10 12:02:44 2004.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: DIAL Failure: "OK"
Date: 10 Dec 2004 17:02:32 GMT
Organization: Columbia University
Lines: 38
Message-ID: <slrncrjll8.5gs.fdc@sesame.cc.columbia.edu>
References: <cp4cc5$gom$1@paperboy.Austria.EU.net> <1102429542.133619.87860@c13g2000cwb.googlegroups.com> <41b97165$0$17046$91cee783@newsreader01.highway.telekom.at>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1102698152 22410 128.59.59.56 (10 Dec 2004 17:02:32 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 10 Dec 2004 17:02:32 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15247
On 2004-12-10, Walter Wagner <chef@via.at> wrote:
:...
: In my opinion the problem is that the zyxel modem is somtimes not
: answering(or answering too slow) and then it happens that the OK from a
: previous command comes back while dialing. And the result is:
:> > ATD56913
:> >
:> > OK
:> > DIAL Failure: 20:50:42: "OK"
:
The DIAL command takes common kinds of problems and modem misbehavior into
account, so it tends to work better than simple OUTPUT/INPUT scripts,
especially ones that don't check for failure and take corrective action.
If you SET DIAL DISPLAY ON you can watch what happens when you give a DIAL
command. If something goes wrong, it retries the operation and/or adapts
automatically in various ways.
: I tried also some other "input" commands, for example: input -1 OK\13\10
: and the failure happend rarely but it was not completly solved!
: And maybe the reason why my USR Modem is working perfect(also with output
: commands), could be because it is an analog modem and there is no need to
: set so much MSN numbers.
:
INPUT has a timeout, and no matter what you value you give (except -1), it
might not be long enough. If you make it too long, then it takes too long
to detect an error. If you make it too short, it reports an error when
it might have succeeded. In any given situation, use trial and error to
arrive at the best value, and code your script to do what you would do
if an error occurred, e.g. reissue the command and wait again (perhaps for
a longer time) for the response. You can find a lot of examples in the
script library:
http://www.columbia.edu/kermit/ckscripts.html
e.g. OUTPUT followed by a looping INPUT, in which actions are governed by
the loop counter.
- Frank